-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ implement Search
for Azure DevOps
#4428
Conversation
5f32f44
to
ad661a9
Compare
ad661a9
to
94b68bb
Compare
Do you think it's worth to add the test with a TODO skip? Similar to scorecard/e2e/code_review_test.go Lines 155 to 156 in a7dac35
|
I didn't realise that was an option. Yeah, I'll add it shortly. I'll hopefully have some news to share on the E2E Azure DevOps front by the next APAC call. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll take a look at the e2e test when added, but otherwise LGTM
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4428 +/- ##
==========================================
+ Coverage 66.80% 68.59% +1.78%
==========================================
Files 230 239 +9
Lines 16602 17830 +1228
==========================================
+ Hits 11091 12230 +1139
+ Misses 4808 4801 -7
- Partials 703 799 +96 |
Signed-off-by: Jamie Magee <[email protected]>
Signed-off-by: Jamie Magee <[email protected]>
I've added an E2E test, but I'm not 100% sure if I've hooked it up correctly with the existing E2E test infrastructure. |
Signed-off-by: Jamie Magee <[email protected]>
06340d0
to
67e0ef1
Compare
Signed-off-by: Jamie Magee <[email protected]>
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
Search
throws an unsupported errorWhat is the new behavior (if this is a feature change)?**
Search
has an implementation for Azure DevOpsWhich issue(s) this PR fixes
Next step of #4177
Special notes for your reviewer
This does not appear to be used in a current check. However, I verified the functionality by writing an E2E test. Unfortunately, I can't check in the E2E test as we don't have an E2E repository configured for Scorecard.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)